Bouncing animation of a lock mode screen in a mobile communication terminal

ABSTRACT

Displaying a lock mode screen of a mobile terminal is disclosed. One embodiment of the present disclosure pertains to a mobile terminal comprising a display module, an input device configured to detect an input for triggering a bouncing animation of a lock mode screen, and a controller configured to cause the display module to display the bouncing animation in response to the input for triggering the bouncing animation, where the bouncing animation comprises the lock mode screen bouncing for a set number of times with respect to an edge of the display module prior to stabilization.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation-in-part application of U.S. patent applicationSer. No. 12/245,692, filed on Oct. 3, 2008 , now abandoned, which claimsthe benefit of earlier filing date and right of priority to KoreanPatent Application No. 10-2007-0100025 filed on Oct. 4, 2007 and KoreanPatent Application No. 10-2008-0082511 filed on Aug. 22, 2008, thecontents of which are all hereby incorporated by reference herein in theentirety.

TECHNICAL FIELD

The present disclosure relates to a method for displaying a lock modescreen, and an apparatus implementing the same.

BACKGROUND

Mobile terminals are devices which may be configured to perform variousfunctions. Examples of such functions include data and voicecommunications, capturing images and video via a camera, recordingaudio, playing music files via a speaker system, and displaying imagesand videos on a display unit. Some mobile terminals include additionalfunctionalities which support online games, multimedia players, etc.More recently, some mobile terminals have been configured to receivebroadcast and multicast signals which permit viewing of contents such asvideos and television programs.

Efforts are ongoing to support and increase the functionalities ofmobile terminals. Such efforts include software and hardwareinnovations. For example, a user interface environment is provided toallow a user to easily and conveniently search or select functionsavailable on mobile terminals, where the user interface environment mayrefer to graphical, textual and auditory information a program presentsto the user, and the control sequences (e.g., keystrokes with a keyboardof the mobile terminals, movements of a mouse of the mobile terminals,or selections with a touch screen of the mobile terminals) the useremploys to control the program. Thus, the user interface environmentmakes it easy, efficient, and enjoyable to operate mobile terminals.

SUMMARY

To achieve these and other objectives and in accordance with the purposeof the present disclosure, as embodied and broadly described herein, thepresent disclosure provides in one aspect a mobile terminal comprising adisplay module, an input device configured to detect an input fortriggering a bouncing animation of a lock mode screen, and a controllerconfigured to cause the display module to display the bouncing animationin response to the input for triggering the bouncing animation, wherethe bouncing animation comprises the lock mode screen bouncing for a setnumber of times with respect to an edge of the display module prior tostabilization.

To achieve these and other advantages and in accordance with the purposeof the present disclosure, as embodied and broadly described herein, thepresent disclosure provides in another aspect a method for displaying alock mode screen of a mobile terminal. The method comprises detecting aninput applied to an input device of the mobile terminal. The methodfurther comprises displaying on a display module of the mobile terminala bouncing animation of a lock mode screen if the input is configuredfor triggering the bouncing animation of the lock mode screen, where thebouncing animation comprises the lock mode screen bouncing for a setnumber of times with respect to an edge of the display module prior tostabilization.

Further scope of applicability of the present disclosure will becomeapparent from the detailed description given hereinafter. However, itshould be understood that the detailed description and specificexamples, while indicating preferred embodiments of the disclosed mobileterminal and method, are given by illustration, since various changesand modifications within the spirit and scope of the disclosed mobileterminal and method will become apparent to those skilled in the artfrom this detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will become more fully understood from thedetailed description given below and the accompanying drawings, whichare given by illustration, and thus are not limitative of the presentdisclosure.

FIG. 1 is a schematic block diagram of a mobile terminal according toone embodiment;

FIG. 2 is a front perspective view of the mobile terminal according toone embodiment;

FIG. 3 is a rear view of the mobile terminal in FIG. 2;

FIG. 4 shows a background screen image of the mobile terminal accordingto one embodiment;

FIG. 5 is a flow chart illustrating the process of displaying a menu ofthe mobile terminal according to one embodiment;

FIG. 6A is a view showing a method for calling a tag related to a menuin FIG. 5;

FIG. 6B is a view showing various positions of tags called in FIG. 6A;

FIG. 7A shows a first example of displaying a menu screen by dragging atag in FIG. 6B;

FIG. 7B shows a second example of displaying a menu screen by dragging atag in FIG. 6B;

FIG. 7C shows a third example of displaying a menu screen by dragging atag in FIG. 6B;

FIG. 8 is a view showing a method for displaying a menu screen accordingto a touch format of a tag in FIG. 6B;

FIGS. 9A to 9E are exemplary views for explaining a method fordisplaying a menu screen image in a state that an executed screen imageis displayed according to one embodiment;

FIGS. 10A and 10E are exemplary views of a mobile terminal displaying alock mode screen in a bouncing animation according to one embodiment;

FIGS. 11A and 11B are exemplary views for executing an applicationduring a lock mode of a mobile terminal according to one embodiment; and

FIG. 12 is a flow chart illustrating a process of displaying a lock modescreen in a bouncing animation according to one embodiment.

Reference will now be made in detail to the preferred embodiments of thepresent disclosure, examples of which are illustrated in theaccompanying drawings. If a detailed explanation for a related knownfunction or construction is considered to unnecessarily divert the gistof the present disclosure, such explanation has been omitted but wouldbe understood by those skilled in the art. In describing the presentdisclosure with reference to the accompanying drawings, like referencenumerals are used for the elements performing like function.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Referring to FIG. 1, a mobile terminal 100 according to one embodiment,may be implemented in various configurations or form factors. Examplesof such terminals include mobile phones, smart phones, notebookcomputers, navigation devices, digital broadcast terminals, personaldigital assistants (PDAs), or portable multimedia players (PMP). Themobile terminal 100 may include a wireless communication unit 110, anA/V (Audio/Video) input unit 120, a manipulating unit 130, a sensingunit 140, an output unit 150, a storage unit 160, an interface unit 170,a controller 180, and a power supply unit 190, etc. Greater or fewercomponents may alternatively be implemented.

For example, the wireless communication unit 110 may include a broadcastreceiving module 111, a mobile communication module 112, a wirelessInternet module 113, a short-range communication module 114, and a GPSmodule 115. The broadcast receiving module 111 receives a broadcastsignal and/or broadcast associated information from an externalbroadcast management server via a broadcast channel. The broadcastchannel may include a satellite channel and a terrestrial channel. Thebroadcast managing server may refer to a system that generates andtransmits a broadcast signal and/or broadcast associated information ora server that receives a previously generated broadcast signal and/orbroadcast associated information and transmits the same to a terminal.

Examples of the broadcast associated information may include informationregarding a broadcast channel, a broadcast program, a broadcast serviceprovider, etc. The broadcast signal may include a TV broadcast signal, aradio broadcast signal, and a data broadcast signal, among others. Ifdesired, the broadcast signal may further include a broadcast signalcombined with a TV or radio broadcast signal. The broadcast associatedinformation may be provided also via a mobile communication network and,in this case, the broadcast associated information may be received bythe mobile communication module 112. The broadcast signal may exist invarious forms. For example, it may exist in the form of an electronicprogram guide (EPG) of digital multimedia broadcasting (DMB), electronicservice guide (ESG) of digital video broadcast-handheld (DVB-H), etc.

The broadcast receiving module 111 may be configured to receivebroadcast signals by using various types of broadcast systems. Inparticular, the broadcast receiving module 111 may receive a digitalbroadcast signal by using a digital broadcast system such as multimediabroadcasting-terrestrial (DMB-T), digital multimediabroadcasting-satellite (DMB-S), digital video broadcast-handheld(DVB-H), the data broadcasting system known as media forward link(MediaFLO®), integrated services digital broadcast-terrestrial (ISDB-T),etc. The broadcast receiving module 111 is configured to be suitable forevery broadcast system that provides a broadcast signal as well as theabove-mentioned digital broadcast systems. Broadcast signal and/orbroadcast-associated information received via the broadcast receivingmodule 111 may be stored in the storage unit 160.

The mobile communication module 112 transmits/receives radio signalsto/from at least one of a base station, an external terminal and aserver in a mobile communication network. Such radio signals may includea voice call signal, a video call signal or various types of dataaccording to text/multimedia message transmission/reception. Thewireless Internet module 113 supports Internet access for the mobileterminal 100, and may be internally or externally coupled to the mobileterminal 100. The short-range communication module 114 refers to amodule for supporting short range communications. Some examples ofshort-range communication technology include Bluetooth™, Radio FrequencyIDentification (RFID), Infrared Data Association (IrDA), Ultra-WideBand(UWB), ZigBee™, and the functional or structural equivalents.

The GPS module 115 is a module receives location information from aplurality of artificial satellites. A/V input unit 120 is configured toinput an audio or video signal. The A/V input unit 120 may include acamera module 121 and a microphone module 122. The camera module 121processes image frames of still pictures or videos obtained by an imagesensor in a video capturing mode or an image capturing mode. Theprocessed image frames may be displayed on a display module 151. Theimage frames processed by the camera module 121 may be stored in thememory 160 or transmitted via the wireless communication unit 110. Twoor more camera modules 121 may be provided according to theconfiguration of the mobile terminal 100.

The microphone module 122 may receive sounds (e.g., audible data) via amicrophone in a phone call mode, a recording mode, a voice recognitionmode, and the like, and process it into electrical voice data. Theprocessed audio (voice) data may be converted for output into a formattransmittable to a mobile communication base station via the mobilecommunication module 112 in case of the phone call mode. The microphonemodule 122 may include various types of noise canceling (or suppression)algorithms to cancel (or suppress) noise generated in the course ofreceiving and transmitting audio signals.

The manipulating unit 130 may generate key input data inputted by a userto control various operations of the mobile terminal 100. Themanipulating unit 130 may include a keypad, a dome switch, a touch pad(e.g., a touch sensitive member that detects changes in resistance,pressure, capacitance, etc.), a jog wheel, a jog switch, and the like.In particular, when the touch pad is overlaid on the display module 151in a layered manner, it may be called a touch screen.

The sensing unit 140 detects a current status (or state) of the mobileterminal 100 such as an open/close state of the mobile terminal 100, alocation of the mobile terminal 100, a presence or absence of usercontact with the mobile terminal 100, and generates commands or signalsfor controlling the operation of the mobile terminal 100. For example,when the mobile terminal 100 is a slide type mobile phone, the sensingunit 140 may sense whether the slide phone is opened or closed. Inaddition, the sensing unit 140 can detect whether or not the powersupply unit 190 supplies power or whether or not the interface unit 170is coupled with an external device.

The interface unit 170 serves as an interface with at least one externaldevice connected with the mobile terminal 100. For example, the externaldevices may include wired/wireless headset ports, external power chargerports, wired/wireless data ports, memory card ports, ports forconnecting a device having an identification module (e.g., SIM/UIM/UICCcard), audio input/output (I/O) ports, video I/O ports, earphone ports,or the like. The interface unit 170 may be used to receive inputs (e.g.,data, information, power, etc.) from an external device and transfer thereceived inputs to one or more elements within the mobile terminal 100or may be used to transfer data from the mobile terminal 100 to anexternal device.

The output unit 150 is configured to output an audio signal, a videosignal or an alarm signal. The output unit 150 may include the displaymodule 151, an audio output module 152, an alarm output module 153, andthe like. The display module 151 may output information processed in themobile terminal 100. For example, when the mobile terminal 100 is in thephone call mode, the display unit 151 may display a User Interface (UI)or a Graphic User Interface (GUI) associated with a call or othercommunication. When the mobile terminal 100 is in the video call mode orthe image capturing mode, the display unit 151 may display a capturedand/or received image, a UI, a GUI, and the like.

When the display module 151 and the touch pad are overlaid in a layeredmanner to form a touch screen, the display module 151 may function asboth an input device and an output device. The display module 151 mayinclude at least one of a Liquid Crystal Display (LCD), a Thin FilmTransistor-LCD (TFT-LCD), an Organic Light Emitting Diode (OLED), aflexible display, a three-dimensional (3D) display, for example. Themobile terminal 100 may include two or more display modules (or otherdisplay means) according to its embodiment. For example, the mobileterminal 100 may include an external display unit (not shown) and aninternal display unit (not shown).

The audio output module 152 may output audio data received from thewireless communication unit 110 or stored in the memory 160 in a callsignal reception mode, a call mode, a record mode, a voice recognitionmode, a broadcast reception mode, and the like. Also, the audio outputmodule 152 may provide audible outputs related to a particular function(e.g., a call signal reception sound, a message reception sound, etc.)performed by the mobile terminal 100. The audio output module 152 mayinclude a speaker, a buzzer, or the like. The alarm output module 153may provide outputs to inform about an occurrence of an event of themobile terminal 100. Typical events may include a call signal reception,a message reception, a key signal input, etc. In addition to audio orvideo outputs, the alarm output module 153 may provide outputs in adifferent manner to inform about an occurrence of an event.

For example, the alarm output module 153 may provide outputs in the formof vibrations (or other tactile means). When a call signal, a message,or some other incoming communication is received, the alarm outputmodule 153 may provide tactile outputs (i.e., vibrations) to inform theuser. By providing tactile outputs, the user can recognize theoccurrence of various events. Outputs informing about the occurrence ofan event may be also provided via the display unit 151 or the audiooutput module 152. The storage unit 160 may store software programs orthe like used for the processing and controlling performed by thecontroller 180, or may temporarily store inputted/outputted data (e.g.,a phonebook, messages, still images, video, etc.).

The storage unit 160 may include at least one type of storage mediumincluding a flash memory type, a hard disk type, a multimedia card type,a card-type memory (e.g., SD or DX memory, etc), a Random Access Memory(RAM), a Static Random Access Memory (SRAM), a Read-Only Memory (ROM),and the like. Also, the mobile terminal 100 may cooperate with a networkstorage device that performs the storage function of the memory 160 overa network connection. The controller 180 typically controls the generaloperations of the mobile terminal 100. For example, the controller 180performs controlling and processing associated with voice calls, datacommunications, video calls, and the like. In addition, the controller180 may include a multimedia reproducing module 181 for reproducing (orplaying back) multimedia data. The multimedia reproducing module 181 maybe configured within the controller 180 or may be configured to beseparated from the controller 180.

The power supply unit 190 receives external or internal power andsupplies power required for the operations of the respective elementsunder the control of the controller 180. So far, the mobile terminal 100has been described from the perspective of the functions. Hereinafter,external elements of the mobile terminal 100 will be described from theperspective of their functions with reference to FIGS. 2 and 3. Mobileterminal 100 may be implemented in a variety of differentconfigurations. Examples of such configurations include folder-type,bar-type, swing-type and slide type combinations thereof. For clarity,further disclosure will primarily relate to the slide-type mobileterminal 100. However such teachings apply equally to other types ofterminals.

FIG. 2 is a front perspective view of the mobile terminal 100 accordingto one embodiment. The slide type mobile terminal 100 may comprise afirst body 100A, and a second body 100B configured to be slidably movedin at least one direction with respect to the first body 100A. A statein which the first body 100A is disposed to overlap with the second body100B may be called a closed configuration, and as shown in FIG. 2, astate in which the first body 100A exposes at least a portion of thesecond body 100B may be called an open configuration. The mobileterminal 100 may usually operate in a standby mode in the closedconfiguration, but this mode can be released by the user. Also, themobile terminal 100 may mainly function in a call mode in the openconfiguration, but may be changed to the standby mode according to usermanipulation or after the lapse of a certain time.

At least one case (housing, casing, cover, etc.) constituting theexternal appearance of the first body 100A comprises a first front case100A-1 and a first rear case 100A-2. Various electronic components maybe installed inside the first front case 100A-1 and the first rear case100A-2. One or more intermediate cases may be additionally disposedbetween the first front case 100A-1 and the first rear case 100A-2. Thecase can be formed by injection-molding a synthetic resin, or made of ametallic material such as stainless steel (STS) or titanium (Ti), orsome other appropriate material. The display module 151, a first audiooutput module 152-1, a first camera module 121-1 or a first manipulatingunit 130-1 may be located on the first front case 100A-1 of the firstbody 100A. The display module 151 may include LCD, OLED, and the like,that visually displays information. A touch pad may be overlaid in alayered manner on the display module 151 to allow the display module 151to function as a touch screen to input information.

The first audio output module 152-1 may be implemented as a receiver ora speaker. The first camera module 121-1 may be implemented to besuitable for a user to capture still images or video of a user and soon. The first manipulating unit 130-1 receives a command for recordingor capturing an image of call communication. Like the first body 100A, acase constituting the external appearance of the second body 100B may beformed by a second front case 100B-1 and a second rear case 100B-2. Asecond manipulating unit 130-2 may be disposed at the second body 100B,specifically, on a front face of the second front case 100B-1.

A third manipulating unit 130-3, the microphone module 122 and theinterface unit 170 may be disposed at either the second front case100B-1 or the second rear case 100B-2. The first to third manipulatingunits 130-1, 130-2 and 130-3 may be called a manipulating portion 130,and various methods can be employed for the manipulating portion 130 solong as it can be operated by the user in a tactile manner. Themanipulating portion 130 can be implemented as a dome switch or touchpad that can receive user commands or information according to pushingor touching, or implemented in the form of a wheel, a jog element, ajoystick, or the like to allow user manipulation thereof.

In terms of its functions, the first manipulating unit 130-1 is used forinputting commands such as start, end, scroll or the like, and thesecond manipulating unit 130-2 is used for inputting numbers,characters, symbols, or the like. The third manipulating unit 130-3 canbe operated to support a so-called hot key function (e.g., speeddialing, dedicated key inputs, etc.) for activating a special functionof the mobile terminal 100. The microphone module 122 may be implementedto be suitable for receiving the user's voice and other various sounds.The interface unit 170 may be used as a link (passage or path) throughwhich the mobile terminal 100 can exchange data or the like with anexternal device.

For example, the interface unit 170 may be implemented as one of aconnection port for connecting an earphone to the mobile terminal 100via a fixed or wireless means, a port for short-range communications(e.g., an Infrared Data Association (IrDA) port, a Bluetooth™ port, awireless LAN port, etc.), or power supply ports for providing power toeach element. The interface unit 170 has been described, so its detaileddescription will be omitted. The power supply unit 190 for supplyingpower to the mobile terminal 100 is located at the side portion of thesecond rear case 100B-2. The power supply unit 190 may be, for example,a rechargeable battery that can be detached.

FIG. 3 is a rear view of the mobile terminal 100 according to anexemplary embodiment. With reference to FIG. 3, a second camera module121-2 may additionally be disposed on a rear surface of the second rearcase 100B-2 of the second body 100B. The second camera module 121-2 mayhave an image capture direction which is substantially the opposite tothat of the first camera module 121-1 (see FIG. 1), and may support adifferent number of pixels as that of the first camera module 121-1.

For example, the first camera module 121-1 may be used for lowresolution (i.e., supporting a relatively small number of pixels) toquickly capture an image (or video) of the user's face and immediatelytransmit the same to the other party during video conferencing or thelike. Meanwhile, the second camera module 121-2 may be used for highresolution (i.e., supporting a relatively large number of pixels) inorder to capture more detailed (higher quality) images (or video) whichtypically do not need to be transmitted immediately.

A flash 121-3 and a mirror 121-4 may be additionally disposed adjacentto the second camera module 121-2. When an image of the subject iscaptured with the second camera module 121-2, the flash 121-3illuminates the subject. The mirror 121-4 allows the user to see himselfwhen he wants to capture his own image (self-image capturing) by usingthe second camera module 121-2. The second rear case 100B-2 may furtherinclude a second audio output module 152-2. The second audio outputmodule 152-2 may implement a stereophonic sound function in conjunctionwith the first audio output module 152-1 (See FIG. 2), and may be alsoused for sending and receiving calls in a speaker phone mode.

A broadcast signal receiving antenna 111-1 may be disposed at one sideor region of the second rear case 100B-2, in addition to an antenna thatsupports mobile communications. The antenna 111-1 can be configured tobe retractable from the second body 100B-2. One part of a slide module100C that slidably combines the first body 100A and the second body 100Bmay be disposed on the first rear case 100A-2 of the first body 100A.The other part of the slide module 100C may be disposed on the secondfront case 100B-1 of the second body 100B, which may not be exposed asshown in FIG. 4. In the above description, the second camera module121-2 and so on is disposed on the second body 100B, but suchconfiguration is not meant to be limited.

For example, one or more of the elements (e.g., 111-1, 121-2, 121-3,152-2, etc.), which are disposed on the second rear case 100B-2 in theabove description, may be mounted on the first body 100A, mainly, on thefirst rear case 100A-2. In this case, those elements disposed on thefirst rear case 100A-2 can be protected (or covered) by the second body100B in the closed configuration. In addition, even if the second cameramodule 121-2 is not provided, the first camera module 121-1 may beconfigured to rotate (or otherwise be moved) to thus allow imagecapturing in various directions.

FIG. 4 shows a background screen image of the mobile terminal 100according to one embodiment. As shown, the mobile terminal 100 may notdisplay any menu item on a background image 310 in a standby mode or maysimply display some menu items 321˜323. A tag 330 related to a menudisplay may be displayed to allow the user to touch the tag 330 to dragit in a certain direction to expose the other remaining menu items thatare usually hidden. A tag may be graphical user interface (GUI) objectassociated with a functional interface which allows a user to expose orhide from view other GUI objects on the mobile terminal 100's display.

In some embodiments, the tag 330 may not be displayed, and the user maytouch one portion of the menu screen image 320 instead of the tag 330 soas to drag the menu screen image 320. Namely, one portion of the menuscreen image 320 may be dragged to expose or hide the menu screen image.The method for allowing the menu screen image 320 to appear by dragginga tag 330 will now be described. The menu screen image 320 refers to ascreen with menu items that appear from or are hidden in the backgroundimage 310.

The tag 330 may be displayed in a shape (e.g., an arrow) indicating adirection in which the menu screen image 320 is exposed or a directionin which the tag 330 can be dragged. For example, the tag 330 may have atriangular shape or an arrow shape. Accordingly, the tag 330 may bedisplayed by changing its direction according to whether the menu screenimage 320 is exposed or hidden from view. The menu item displayed on thebackground screen image 310 may include an icon for executing a program.In addition, the menu item may include a ‘group menu item’ 430 forretrieving a menu item of a different group and displaying it on thebackground screen.

As shown in FIG. 7C, a ‘group menu item’ 430 may be displayed in theshape that can be discriminated from the menu item for executing theprogram. However, it may not be limited to the shape as shown in FIG.7C. Menu screen image 320, which refers to a screen image including aplurality of menu items (or icons), is visually distinguished from thebackground screen image(s) 310 and may be translucent (i.e.,semi-transparent) to allow the background screen image(s) 310 to be seenthere through. In this case, an environment setting menu may be providedto allow the degree of transparency of the menu screen to be adjusted.

The menu screen image 320 may expose some of the menu items while hidingother items according to the distance along which the tag 330 isdragged. Namely, some of the menu items may be displayed while othersmay not be displayed according to the drag distance. Also, thecontroller 180 may determine the type of touch that was or is beingperformed when the user touches or releases the tag (icon) 330 basedupon at least one of the number of touches, a contact time, contactspeed, contact direction, contact pressure and contact surface area, orany combination thereof.

The type of touch may include pushing or pulling (or otherwise moving)the tag 330 or icon on the screen in an upward, downward or some otherdirection in a rather abrupt movement, which may be referred to as“flicking” because the movement, in one embodiment, may be compared tothe motion associated with flicking a page of a book, for example. Whenthe tag 330 is flicked in such a manner, the entire menu screen image320 can be automatically shown (or exposed) or hidden such that theimage appears to be unfolding on the screen without having to drag theentire menu screen image 320 all the way across the screen.

The respective menu items displayed on the menu screen image 320 may beindicated by icons of certain shapes or images. The menu items may bearranged in an arbitrary format by combining rows and columns or may bearranged randomly by disregarding rows and columns. The menu screenimage 320 may be shown at or be hidden from a particular region of thescreen, by setting at least one of a side portion, a corner portion, ora central portion of the touch screen as a boundary region from whichthe menu screen image 320 can appear or disappear, and the tag 330 (orother graphical indicator) can be used to indicate the boundary region.

FIG. 5 is a flow chart illustrating the process of displaying a menu ofthe mobile terminal 100 according to one embodiment. The method ofdisplay process of the mobile terminal 100 according to the presentdisclosure will now be described with reference to FIGS. 5, 6A, 6B, 7A,7B, 7C and 8. For the sake of example, it is assumed that no menu itemis displayed on the background screen image 310 of the mobile terminal100. As shown in FIG. 6A, if there is nothing displayed on thebackground screen image 310 with respect to a menu item, the user maytouch the background screen image 310 to display tags 410 to display amenu screen image 320. That is, when a touch is inputted with nothingdisplayed on the background screen image 310, the tags 410 related tothe menu screen image 320 are displayed (S101 to S103).

As shown in FIG. 6B, one or more tags 411 to 416 may be displayed, andthe tags 410 may be displayed at one of a side, a corner or an internalregion of the touch screen. If a tag related to the menu display isalready displayed on the background screen image 310, the tag callingprocess may be omitted. After the tag is displayed, if there is nodragging or flicking during a pre-set time, the displayed tag may bereleased. With the tags 410 displayed, when the user touches one of thetags 410 and drags it (S104), the controller 180 exposes a menu screenimage 320, which has been hidden, in the direction in which the tag isdragged as shown in FIGS. 7A to 7C. Likewise, if the tag is dragged in adifferent direction, an exposed menu screen image 320 may be hidden(S105).

The menu items displayed on the menu screen image 320 may include agroup menu item 430 indicating a menu item included in a different menugroup, and it may be displayed to be different from the menu items 420for executing a program. If tag dragging is stopped before the entiremenu screen image 320 is exposed, or when the touch to the tag beingdragged is released, the menu screen maintains a currently exposed stateas it is. That is, while flicking results in exposing or hiding theentire menu screen image 320, dragging allows adjusting of the degree ofexposing or hiding of the menu screen image 320 in accordance with thespeed and direction of the dragging motion.

Notably, referring back for FIG. 5, if the user wants to quickly exposeor hide the entire menu screen image 320, he may flick a desired tag byfor example interactive with the tag successively (e.g., tapping on thetag), or as shown in FIG. 8, the user may push the tag up or down in abouncing manner (S106, S107). In order to determine a touch input type(i.e., whether the user means to flick or drag the tag), the controller180 may use one or more factors associated with user interaction withthe tag. These factors may include time, speed, direction, pressure andarea to which the touch is applied or released.

The method for displaying a menu screen image 320 when a screen imageexecuting a particular menu is displayed on a background screen will nowbe described with reference to FIGS. 9A to 9E. As shown in FIG. 9A, ifit is assumed that a particular menu has been already executed and thecorresponding execution screen image 510 is displayed on the backgroundscreen image 310, if the region of the exposed menu screen increases,the size of the region where the executed screen image 510 is displayedwould be reduced inverse-proportionally. For example, if the menu screenimage 320 is dragged to appear in a state that a video reproductionimage has been displayed, the region of the exposed menu screen image320 is gradually increased while the size of region where the videoreproduction image is displayed is gradually reduced.

A display position of the re-sized executed screen image 510 may varyaccording to a direction in which the menu screen image 320 is dragged.For example, as shown in FIG. 9A, when the menu screen image 320 isdragged in a downward direction, the re-sized executed screen image 510may be displayed at an upper portion. As shown in FIG. 9B, if the menuscreen image 320 is dragged from the right side, it may be displayed atthe left portion. In addition, as shown in FIG. 9C, if the menu screenimage 320 is dragged from one corner portion, the executed screen image510 may be displayed at a corner potion of its opposite side. As shownin FIG. 9D, even if the menu screen image 320 is dragged from one cornerportion, the executed screen image 510 may be displayed at up/downportion (a) or left/right portion (b).

With reference to FIGS. 9A and 9C, the re-sizing method of the executedscreen image 510 may vary according to the direction in which the menuscreen image 320 is dragged. For example, if the menu screen image 320is dragged in an upward direction or in a downward direction, the lengthof the vertical direction (up/down direction) of the executed screenimage 510 is adjusted while the length of the horizontal direction ofthe executed screen image 510 is maintained. If the menu screen image320 is dragged in a left direction or in a right direction, the lengthof the horizontal direction (left/right direction) of the executedscreen image 510 is adjusted while the length of the vertical directionof the executed screen image 510 is maintained. If the menu screen image320 is dragged from a corner portion, the both lengths of the horizontaland vertical directions of the executed screen image 510 can beadjusted.

Instead of adjusting the size of the executed screen image 510 accordingto an environment setting option, a portion of the region where theexecuted screen image 510 like the menu screen image 320 is displayedmay be allowed to appear or be hidden as shown in FIG. 9E. Namely, asthe exposure region of the menu screen image 320 increases, the exposureregion of the executed screen image 510 may be reducedinverse-proportionally. Also, as the exposure region of the menu screenimage 320 is reduced, the exposure region of the executed screen image510 may be increased inverse-proportionally.

The controller 180 controls the operation of resizing or exposing/hidingthe executed screen image 510 according to an exposing/hiding operationof the menu screen image 320. In the above description, tags 410 aredisplayed on the menu screen image 320 and a desired tag being displayedis touched to be dragged or flicked to display a menu screen image 320.However, even without tags 410 for controlling display of the menuscreen image 320, the above-described menu screen display function maybe executed when the background screen image 310 is touched for aparticular time period and then dragged or flicked. In this case, atouch unit for touching, dragging and flicking may be the user's fingeror a stylus, or any other means that have not been mentioned.

FIGS. 10A and 10E are exemplary views of a mobile terminal 510displaying a lock mode screen 560 in a bouncing animation according toone embodiment. In FIGS. 10A and 10B, the mobile terminal 510 (e.g., amobile phone, a tablet TV, a laptop, etc.) comprises a display module540 and an input device (e.g., which may be a part of the manipulatingunit 130, such as a touch pad) configured to detect an input fortriggering the bouncing animation of the lock mode screen 560. It isappreciated that the display module 540 is an exemplary embodiment ofthe display unit 151 in FIG. 1. The mobile terminal 510 furthercomprises the controller (180) configured to cause the display module540 to display the bouncing animation in response to the input fortriggering the bouncing animation, where the bouncing animationcomprises the lock mode screen 560 bouncing for a set number of timeswith respect to an edge (e.g., a bottom edge) of the display module 540prior to stabilization. As described in FIG. 1, when the display module540 and the input device are overlaid in a layered manner to form atouch screen, the display module 540 may function as both an inputdevice and an output device.

FIG. 10A illustrates a process of displaying the lock mode screen 560 inthe bouncing animation upon pressing a hard key 520 to convert from asuspend mode screen 550 to the lock mode screen 560. In FIG. 10A, theinput device configured to detect the input for triggering the bouncinganimation of the lock mode screen 560 comprises the hard key 520. Inprocess (a) of FIG. 10A, the hard key 520 is pressed by a user 530(e.g., a finger of the user 530) to convert the mobile terminal 510 inthe suspend mode screen 550 (e.g., a sleep mode screen where the LCD orother lighting element for the display module 540 is off) into the lockmode screen 560 (e.g., a suspend mode screen or a sleep mode screen) Inone example embodiment, the lock mode screen 560 is a lock screen or ascreensaver.

In process (b), the lock mode screen 560 moves upward to expose anactive mode screen 570 (e.g., or a play mode screen) underneath the lockmode screen 560, where the active mode screen 570 may comprise one ormore icons representing applications, widgets, or contents. In process(c), the lock mode screen 560 moves even further from the bottom edge ofthe display module 540 such that more of the active mode screen 570 isexposed. This may allow the user 530 to take a peek at the layout detailof the active mode screen 570. In process (d), the lock mode screen 560is dropped to the bottom of the display module 540 such that the activemode screen 570 is no longer available for peeking.

Although FIG. 10A illustrates the bouncing animation where the lock modescreen 560 moves up and down once, in one exemplary implementation, thecontroller 180 is configured to have the lock mode screen 560 to bouncemore than two times. Further, in another exemplary implementation, thecontroller 180 is configured to cause the display module 540 to performthe bouncing of the lock mode screen 560 in a certain speed (e.g., 2seconds to complete a single bounce). In yet another exemplaryimplementation, the controller 180 is configured to have the lock modescreen 560 to move in different heights as multiple bounces of the lockmode screen 560 are performed. For example, the first bounce may be onemillimeter in height from the bottom of the display module 540, thesecond bounce two millimeters in height from the bottom, and the thirdbounce three millimeters in height from the bottom followed by thefourth bounce two millimeters in height from the bottom and the fifthbounce one millimeter in height from the bottom until the lock modescreen 560 comes to rest.

FIG. 10B illustrates a process of displaying the lock mode screen 560 inthe bouncing animation upon pressing a hard key 520 to convert themobile terminal 510 from the active mode screen 570 to the lock modescreen 560. In process (a) of FIG. 10B, the hard key 520 is pressed bythe user 530 to convert the mobile terminal 510 in the active modescreen 570 into the lock mode screen 560. In process (b), the lock modescreen 560 moves downward to hide the active mode screen 570. It isappreciated that there may be a brief period of a pause mode screenbetween the active mode screen 570 in process (a) and the lock modescreen 560 in process (b). In process (c), the lock mode screen 560 isdropped to the bottom of the display module 540 such that the activemode screen 570 is no longer available for peeking.

In process (d), the lock mode screen 560 bounces upward in apreconfigured height to expose a bottom portion of the active modescreen 570. In process (e), the lock mode screen 560 is dropped to thebottom of the display module 540 such that the active mode screen 570 isno longer available for peeking In process (f), when there is no inputregistered for the mobile terminal 510 for more than a threshold time(e.g., 30 seconds), the mobile terminal 510 enters into a suspend modeor sleep mode, thus displaying the suspend mode screen 550 on thedisplay module 540. In FIG. 10B, the controller 180 is configured toperform the bouncing animation illustrated in processes (a) through (f)in varying speeds, heights, and number of repetitions.

FIG. 10C illustrates a process of displaying the lock mode screen 560 inthe bouncing animation upon tapping the display module 540. In FIG. 10C,the display module 540 and the input device are overlaid in a layeredmanner to form a touch screen on the mobile terminal 510, so the displaymodule 540 may function as both an input device and an output device. Inprocess (a) of FIG. 10C, the surface of the display module 540 is tapped(e.g., touched or contacted) by the user 530 to trigger the bouncinganimation of the lock mode screen 560. In process (b), the lock modescreen 560 moves upward to expose an active mode screen 570, where theactive mode screen 570 may comprise one or more icons representingapplications, widgets, or contents.

In process (c), the lock mode screen 560 moves even further from thebottom edge of the display module 540 such that more of the active modescreen 570 is exposed. This may allow the user 530 to take a peek at thelayout detail of the active mode screen 570. In process (d), the lockmode screen 560 is dropped to the bottom of the display module 540 suchthat the active mode screen 570 is no longer available for peekingAlthough FIG. 10C illustrates the bouncing animation where the lock modescreen 560 moves up and down once, the controller 180 may be configuredto have the lock mode screen 560 to perform the bouncing animationillustrated in processes (a) through (d) in varying speeds, heights, andnumber of repetitions. In one embodiment, the number of bouncesperformed during the bouncing animation is determined by strength of thetap applied to the surface of the display module 540 or touch screen.

FIG. 10D illustrates a process of displaying the lock mode screen 560 inthe bouncing animation upon dragging or flicking an edge of the lockmode screen 560. In one embodiment, as illustrated in process (a) ofFIG. 10D, the bouncing animation of the lock mode screen 560 isinitiated by touching and dragging the lock mode screen 560 by a length.In an alternative embodiment, the bouncing animation of the lock modescreen 560 is initiated by flicking the lock mode screen 560. In yetanother alternative embodiment, the dragging of the lock mode screen 560initiates the bouncing animation, whereas the flicking of the lock modescreen 560 curtains up the lock mode screen 560, thereby exposing theactive mode screen 570 underneath the lock mode screen 560 in itsentirety. It is appreciated that processes (b) through (h) in FIG. 10Dis similar to the bouncing animation illustrated in processes (b)through (d) in FIG. 10A, processes (b) through (e) in FIG. 10B, orprocesses (b) through (d) in FIG. 10C.

In one embodiment, the controller 180 is configured to perform thebouncing animation illustrated in processes (a) through (h) of FIG. 10Din varying speeds, heights, and number of repetitions. In oneembodiment, the number of bounces performed during the bouncinganimation is determined by a distance of the dragging of the lock modescreen 560. For instance, as the motion of the dragging covers morelength, then there would be more bounces occurring during theperformance of the bouncing animation. In another embodiment, the numberof bounces performed during the bouncing animation is determined bystrength of the flicking applied to the display module 540. Forinstance, as more force is applied during the flicking motion, therewould be more bounces occurring during the performance of the bouncinganimation.

Further, in one embodiment, as illustrated in processes (a), (c), (d),and (e), the controller 180 is configured to display the lock modescreen 560 in a different degree of transparency as the lock mode screen560 is moving along the display module 540. In one exampleimplementation, as the bouncing animation is triggered in process (a),the lock mode screen 560 is opaque where none of the active mode screen570 is seen through the lock mode screen 560. In process (c), as thelock mode screen 560 moves upward, the lock mode screen 560 become moretransparent (e.g., translucent) such that a glimpse of the active modescreen 570 may be seen through the lock mode screen 560 to some degree.Then, in process (d), as the lock mode screen 560 reaches toward the topedge of the display module 540, the lock mode screen 560 may become moretransparent such that the active mode screen 570 may be exposed in agreater detail. Further, texts or images 580 present on the lock modescreen 560 may be diluted increasingly as the lock mode screen 560 movesupward toward the edge of the display module 540.

In another example implementation (which is not shown), as the bouncinganimation is triggered in process (a), the lock mode screen 560 isopaque throughout the process of the bouncing animation, except when thelock mode screen 560 is hitting the bottom edge of the display module540 or the touch screen to bounce back. When the lock mode screen 560(e.g., the lock screen) hits the bottom of the display module 540 tobounce back, the lock mode screen 560 becomes transparent to expose thedetails of the active mode screen 570. Further, the texts or images 580present on the lock mode screen 560 may be diluted as the lock modescreen 560 hits the bottom edge of the display module 540.

It is appreciated that the bouncing animation may be performed in anyconfigured direction, although FIG. 10D illustrates the lock mode screen560 bouncing at the bottom edge of the display module 540. For example,the controller 180 may be configured to display the bouncing animationin such a way that the lock mode screen 560 bouncing at the top of thedisplay module 540 when dragged or flicked from the top to bottom of thedisplay module 540, bouncing at one or both sides of the display module540 when dragged or flicked from the opposite side of the display module540, or bouncing at one corner of the display module 540 when dragged orflicked from the diagonally opposite corner of the display module 540.

FIG. 10E illustrates a process of displaying the lock mode screen 560 inthe bouncing animation upon receiving an incoming call. In oneembodiment, as illustrated in process (b) of FIG. 10E, the bouncinganimation of the lock mode screen 560 is initiated upon receiving anincoming call or an incoming message (e.g., a text message, a videomessage, an audio message, or a multi-media message). Upon receiving theincoming call, a caller identification (ID) 590 is displayed on thedisplay module 540, and the lock mode screen 560 moves upward to exposethe active mode screen 570 underneath it. In process (c), the controller180 is configured to display a first soft key for answering the incomingcall 591 (e.g., “answer”) and a second soft key for ignoring theincoming call (e.g., “ignore”) on the active mode screen 570 underneaththe lock mode screen 560.

In one example implementation, when the incoming call is answered bypressing the first soft key for answering the incoming call 591, thelock mode screen 560 is cleared, thus making a way for the active modescreen 570. In another example implementation, when the incoming call isignored by pressing the second soft key for ignoring the incoming call592, the bouncing animation of the lock mode screen 560 is initiated inresponse to a signal indicating a selection of the second soft key 592.

In one embodiment, the controller 180 is configured to perform thebouncing animation illustrated in processes (a) through (g) of FIG. 10Ein varying speeds, heights, and number of repetitions in response to theselection of the second soft key 592. In one embodiment, the number ofbounces performed during the bouncing animation may be determined by aduration of the ringing of the incoming call. For instance, if theincoming call continues ringing without any response registered to themobile terminal 510, the bouncing animation is continuously performeduntil one of the soft keys is pressed.

Further, in one embodiment, as illustrated in processes (a) through (d),the controller 180 is configured to display the lock mode screen 560 ina different degree of transparency as the lock mode screen 560 is movingalong the display module 540. For example, as the bouncing animation istriggered in process (a), the lock mode screen 560 is opaque where noneof the active mode screen 570 is seen through the lock mode screen 560.In process (b), as the lock mode screen 560 moves upward, the lock modescreen 560 becomes more transparent (e.g., translucent) such that aglimpse of the active mode screen 570 may be seen through the lock modescreen 560 to some degree. Then, in process (c), as the lock mode screen560 reaches toward the top edge of the display module 540, the lock modescreen 560 may become even more transparent such that the active modescreen 570 may be seen through the lock mode screen 560 in even moredetails. Further, the texts or images 580 present on the lock modescreen 560 may be diluted increasingly as the lock mode screen 560 movesupward toward the edge of the display module 540. It is appreciated thatexemplary processes illustrated in 10A to 10E with respect to thebouncing animation of the lock mode screen 560 (e.g., the lock screen)may provide an aesthetic view of the lock mode screen 560 implemented onthe mobile terminal 510.

FIGS. 11A and 11B are exemplary views for executing an applicationduring a lock mode or locked screen mode of a mobile terminal accordingto one embodiment. More particularly, FIG. 11A illustrates an exemplaryview of the mobile terminal 510 executing an application on the activemode screen 570 while the lock mode screen 560 (e.g., the lock screen)is still active. When the user 530 touches (e.g., flicks or drags) thedisplay module 540 using the user's finger or a stylus as shown inprocess (a), the lock mode screen 560 moves (e.g., slides or glides) uptoward the top edge of the mobile terminal 510 as illustrated in process(b).

In process (b), while the lock mode screen 560 is open enough to exposesome of the applications, widgets, or contents available on the activemode screen 570, the user 530 may select one of the applications,widgets, or contents. For example, in process (b), the user 530 selectsa calendar 610 (e.g., an application or a widget) on the active modescreen 570 by making a contact with the icon representing the calendar610. In process (b), the lock mode screen 560 becomes more transparentas it moves towards the edge of the display module 540, and the text orimage 580 on the lock mode screen 560 becomes increasingly diluted inthe process. Process (c) illustrates an executed view of the calendar620. In one embodiment, once the calendar 610 is deactivated and thereis no further input to the active mode screen 570 for more than athreshold time (e.g., 30 seconds), the controller 180 is configured toexecute the bouncing animation of the lock mode screen 560 as the modeof the mobile terminal 510 is transformed from the active mode to thelock mode.

FIG. 11B illustrates an exemplary view of the mobile terminal 510executing an application on the active mode screen 570 while the lockmode screen 560 (e.g., the lock screen) is temporarily stopped. Inprocess (a) of FIG. 11B, when the user 530 touches (e.g., flicks ordrags) the display module 540 using the user's finger or stylus as shownin process (a), the lock mode screen 560 moves (e.g., slides or glides)up toward the top edge of the mobile terminal 510.

In process (b), when the lock mode screen 560 is open enough to exposesome of the applications, widgets, or contents available on the activemode screen 570, the user 530 may stop the movement of the lock modescreen 560 by pressing the bottom edge of the lock mode screen 560.Then, the user 530 may select one of the applications, widgets, orcontents available on the active mode screen 570. For example, inprocess (c), the user 530 selects the calendar 610 (e.g., an applicationor a widget) on the active mode screen 570 by making a contact with theicon representing the calendar 610. Process (d) illustrates the executedview of the calendar 620. Then once the calendar 610 is deactivated andthere is no further input to the active mode screen 570 for more than athreshold time (e.g., 30 seconds), the controller 180 is configured toexecute the bouncing animation of the lock mode screen 560 while themode of the mobile terminal 510 is transformed from the active mode tothe lock mode.

FIG. 12 is a flow chart illustrating a process of displaying a lock modescreen in a bouncing animation according to one embodiment. The methodof displaying the lock mode screen in the bouncing animation is nowdescribed with reference to FIGS. 10A, 10C, 10D, 11A, and 11B. Inprocess (a) of FIGS. 10A, 10C, and 10D, the bouncing animation of thelock mode screen 560 is initiated as the input triggering the bouncinganimation is detected (step 201). Then the bouncing animation of thelock mode screen 560 is displayed (step 202) as in process (b) of FIGS.10A, 10C, and 10D. In process (c) of FIGS. 10A and 10C and in process(d) of FIG. 10D, the active mode screen 570 with one or moreapplications are exposed (step 203) underneath the lock mode screen 560.

In FIG. 12, if there is no touch input applied (step 204) and noapplication selected during the exposure of the active mode screen 570(step 205), then the bouncing animation continues until its completion(step 207) as illustrated in process (d) of FIGS. 10A and 10C andprocess (h) in FIG. 10D. If a touch input applied on an edge of the lockmode screen 560 is detected (step 204), as illustrated in process (b) ofFIG. 11B, then the movement of the lock mode screen 560 is stopped (step208) to give the user 530 time to select any application on the activemode screen 570 available for access. Then, when the application isselected by the user 530, the application is executed (step 206).However, if there is no touch input applied on the edge of the lock modescreen 560, but the application is selected by the user 530 while theapplication on the active mode screen 570 is available for selectionunderneath the lock mode screen 560, the application is executed (step206).

As the exemplary embodiments may be implemented in several forms withoutdeparting from the characteristics thereof, it should also be understoodthat the above-described embodiments are not limited by any of thedetails of the foregoing description, unless otherwise specified, butrather should be construed broadly within its scope as defined in theappended claims. Therefore, various changes and modifications that fallwithin the scope of the claims, or equivalents of such scope aretherefore intended to be embraced by the appended claims.

What is claimed is:
 1. A mobile terminal comprising: a touch screen; anda controller configured to: cause displaying of a lock screen on thetouch screen; cause displaying of at least a portion of an active screenon the touch screen in response to a dragging of the lock screen; changea degree of a transparency of text on the lock screen according to thedragging such that the text is displayed in at least two differentdegrees of transparency; and cause displaying of a bouncing animation ofthe lock screen after the dragging such that the lock screen bouncesmultiple times against a single edge of the touch screen according to aset number of times.
 2. The mobile terminal of claim 1, wherein thecontroller is further configured to cause the displaying of the bouncinganimation in response to tapping on the lock screen.
 3. The mobileterminal of claim 1, further comprising a wireless communication unit,wherein the wireless communication unit is configured to receive anincoming call.
 4. The mobile terminal of claim 3, wherein the controlleris further configured to cause displaying of a first soft key foranswering incoming call and a second soft key for ignoring the incomingcall on the active screen which is laid underneath the lock screen. 5.The mobile terminal of claim 4, wherein the controller is furtherconfigured to repeat the bouncing animation in response to a signalindicating a selection of the second soft key.
 6. The mobile terminal ofclaim 1, wherein the controller is further configured to stop thebouncing of the lock screen in response to a touch applied during thebouncing animation to an area on the touch screen which corresponds toan edge of the lock screen.
 7. A method for displaying a lock modescreen of a mobile terminal comprising a touch screen, the methodcomprising: displaying the lock screen on the touch screen; displayingat least a portion of an active screen on the touch screen in responseto a dragging of the lock screen; changing a degree of a transparency oftext on in the lock screen according to a the dragging such that thetext is displayed in at least two different degrees of transparency; anddisplaying a bouncing animation of the lock screen on the touch screenafter the dragging, such that the lock screen bounces multiple timesagainst a single edge of the touch screen according to a set number oftimes.
 8. The method of claim 7, further comprising moving the lockscreen in response to an additional input applied to the input device ofthe mobile terminal to expose the active screen of the mobile terminalwhich is laid underneath the lock screen, wherein the active screencomprises an icon representing an application.
 9. The method of claim 8,further comprising executing the application in response to a selectionof the icon representing the application.
 10. The method of claim 8,further comprising stopping the bouncing of the lock screen in responseto a touch input applied during the bouncing animation to an edge of thelock screen.
 11. The method of claim 10, further comprising executingthe application in response to a selection of the icon representing theapplication.
 12. A non-transitory computer readable storage mediumhaving a processing program stored thereon, wherein the processingprogram is configured to operate a processor of a mobile terminal toperform: displaying a lock screen on a touch screen of the mobileterminal; displaying at least a portion of an active screen on the touchscreen in response to a dragging of the lock screen; changing a degreeof a transparency of text on the lock screen according to the draggingsuch that the text is displayed in at least two different degrees oftransparency; and displaying a bouncing animation of the lock screenafter the dragging, such that the lock screen bounces multiple timesagainst a single edge of the touch screen according to a set number oftimes.
 13. A mobile terminal comprising: a touch screen; and acontroller configured to: cause the touch screen to display a lockscreen comprising at least one visual object, wherein the lock screenhides an active screen comprising at least one icon representing atleast one application, widget, or content behind the lock screen; movethe displayed lock screen upward in response to a single touch andmoving input applied to the lock screen in an upward direction, whereinas the lock screen moves more upward, the at least one visual objectbecomes more transparent such as that the at least one visual object isdisplayed in at least two different degrees of transparency and theactive screen is increasingly exposed during the upward movement of thelock screen; and bounce the lock screen multiple times against a bottomedge of the touch screen according to a set number of times moved lockscreen is released from the touch.
 14. The mobile terminal of claim 13,wherein the lock screen moves in different heights as the lock screenbounces for the multiple times.
 15. The mobile terminal of claim 13,wherein the lock screen is, configured to bounce at least twice, and aheight of a first bouncing of the lock screen is higher than a height ofa second bouncing of the lock screen.
 16. The mobile terminal of claim13, wherein the visual object comprises a text.
 17. The mobile terminalof claim 13, wherein the touch and moving input comprises a drag input.18. A method of a mobile terminal comprising a touch screen, the methodcomprises: displaying a lock screen comprising a visual object on thetouch screen, wherein the lock screen hides an active screen comprisingat least one icon representing at least one application, widget, orcontent behind the lock screen; moving the lock screen upward inresponse to a single touch and moving input applied to the lock screenin an upward direction, wherein as the lock screen moves more upward,the visual object becomes more transparent such that the at least onevisual object is displayed in at least two different degrees oftransparency and the active screen is increasingly exposed during theupward movement of the lock screen; and bouncing the lock screenmultiple times against a bottom edge of the touch screen according to aset number of times moved lock screen is released from the touch. 19.The method of claim 18, wherein the lock screen moves in differentheights as the lock screen bounces for the multiple times.
 20. Themethod of claim 18, further comprising executing an application of theat least one application in response to a selection of an iconrepresenting the application.
 21. The mobile terminal of claim 1,wherein the lock screen is moved in a different height time the lockscreen is bounced during the bouncing animation.
 22. A mobile terminalcomprising: a touch screen configured to receive a first input fortriggering a bouncing animation of a lock screen; an input unitconfigured to receive a second input for triggering the bouncinganimation of the lock screen, the input unit excluding the touch screen;and a controller configured to: cause displaying of the lock screen onthe touch screen; and cause displaying of the bouncing animation on thetouch screen in response to the first or second input, wherein thebouncing animation comprises the lock screen bouncing multiple timesagainst a single edge of the touch screen according to a set number oftimes, and wherein the first input comprises a dragging of the lockscreen such that a degree of a transparency of text included in the lockscreen is changed incrementally as the lock screen is moved farther froman origin of the dragging such that the text is displayed in at leasttwo different degrees of transparency, and the bouncing animation isinitiated in response to the dragging.
 23. The mobile terminal of claim22, wherein the second input is received via the unit positioned at aportion of a case of the mobile terminal.
 24. The mobile terminal ofclaim 2, wherein the set number of times is different based on whetherthe bouncing animation is initiated in response to the dragging or thetapping.
 25. The mobile terminal of claim 1, wherein the controller isfurther configured to cause the lock screen to move in different heightsas the lock screen bounces for the multiple times.
 26. The mobileterminal of claim 1, wherein: the controller is further configured tocause the lock screen to bounce at least twice; and a height of a firstbouncing of the lock screen is higher than a height of a second bouncingof the lock screen.